0.1 Introduction

The CTT Node™ is a mini-base-station that allows you to localize LifeTags™, PowerTags™ and HybridTags™ with a high degree of accuracy. If deployed in a grid fashion, and employing post-hoc analysis, the CTT Nodes can operate as pseudo-reverse-GPS, providing near GPS accuracy in optimal conditions. With the addition of calibration data, Nodes can provide presence/absence and distance estimate of instantaneous detections from supported tags.

The CTT Node uploads received tag detection data to the standard CTT SensorStation™, creating a dense, high resolution tracking network. Solar power recharges batteries in the CTT Nodes meaning no extra power cables or external solar systems are necessary.

Each CTT Node has a detectable range of about 250-300 meters, and is able to relay data to a CTT Base Station as far away as several kilometers.

0.2 Node Setup

Because of shipping laws, your node arrives with a partially-charged Lithium battery and should be placed in the sun for several days prior to deployment to get its battery up to full charge. When your node arrives you will notice a few things.

0.2.1 Unboxing

Node packaged for shipping

Remove the packing material that surrounds your node. You can do this by removing the two nuts on the mounting bracket, which will then allow you to slide the bubble wrap off of the node and save it for future use.

Notice that there is a piece of blue tape securing a magnet to the node.

Node with bubblewrap removed

This magnet operates the switch that determines whether your node is searching for tags. Note that even with the magnet on the node, your node will send health reports every five minutes. It can do this on a fully charged battery for over two years without charging, so is fine for storage. Once you remove the magnet, though, your node will function for roughly one week without a charge. We recommend only removing the magnet when deploying your nodes, or for temporary testing.

Note the black dot on the node indicates where the magnet must be aligned when not in use

Once you deploy your nodes, be sure to save the magnets for future use.

0.3 Attaching Your Node

Each node comes with the necessary hardware for mounting it to various materials. We typically recommend 3/4" or 1/2" EMT conduit, but you can mount it to practically anything. We recommend mounting your node either horizontally, with the solar panel facing the sky, or vertically, with the solar panel facing south, for optimal recharging performance.

0.3.1 A note about solar recharging

Note that mounting your node in shade, or canopy cover, will reduce recharge times and may require you to periodically move the node to a sunny location for recharging, or subsidize the node with an additional battery back (each node comes with a USB port which can be used for attaching an additional power supply).

0.4 SensorStation Pairing

There is no need to pair a node to a SensorStation. Simply placing the node within the range of a SensorStation antenna will cause the SensorStation to detect and process node data.

0.5 Operation Tips

As a rule of thumb we recommend placing all nodes within 1-1.5km of a SensorStation. It is possible to increase the distance depending on your choice of antennas, but this distance has proved effective for many installations. Topography, density of vegetation, and other factors may impact the detection distance.

Since each node transmits health information every five minutes, one good benchmark when testing you nodes is to ensure that your SensorStation is detecting each node at least every five minutes. If not, you will likely be losing some data which will only be recoverable by opening the node, removing and reading the internal SD card. Put another way, any data not received by the SensorStation will not be sent later, but resides only on the internal node SD card.

0.5.1 Connecting to the external USB port

Node with USB cover installed

Node with USB cover removed, exposing 4 pins

Node with 4-pin to USB-A adapter inserted

0.5.2 Opening your Node

If you need to access the internal SD card, or troubleshoot a node, you can access it by removing the single screw on the bottom of the case, and separating the top of the node from the bottom with a little squeeze and pull procedure.

First remove the screw in the bottom of the Node

Then apply equal pressure to the long sides of the case, and pull the top and bottom apart

Closeup of the Node board

On the board you will notice several buttons. Pressing them has the corresponding effect:

  • SW1 - Forces the node to restart.
  • SW2 - Forces the node to send a health message (requires a SensorStation to determine success).
  • SW3 - Forces the node to look for new firmware on the SD card, and if it finds it, to install it.

The Micro USB port is also apparent in the lower right side of the board, and labled USB. You can use this port to connect your node directly to a computer.

0.6 Test Transmit

0.7 Advanced Configuration via Node Client

You can use a development program we’ve created called Node Client to troubleshoot your node and modify several parameters. The latest version of Node Client can be downloaded from our support Slack workspace. If you don’t already have access, please email us at . You can connect your node to a computer using either the provided 4-pin -> USB adapter and the port on the underside of the node, or the micro-usb port directly on the board (after opening the node).

Opening screen of Node Client

Upon opening Node Client you will see the main screen with Steps 1 - 4 outlined. The window to the right is actually a screenshot of Device Manager - not Device Manager itself (hence “Figure 1”), but gives you an idea of what your Device Manager should look like if you have the proper dirvers installed. If not, the blue link that says “Driver” can be clicked to take you to the download page. You must have the Silicon Labs driver installed to run Node Clien.

Clicking on Update Ports should populate both steps 2 and 3 values. If not you may need to install the proper driver.

With the proper driver installed, you can click on Update Ports which will then populate Steps 2 and 3 with values for available COM ports and default Baud Rate. You may have multiple COM ports available, so ensure that the one selected refers to your Silicon Labs driver port.

Clicking Open will open the USB connection between the Node and your computer.

Once you have selected the appropriate port and baud rate, click the Open button in Step 4.

Once the port is open, the button under Step 4 will show Close. Clicking on it again will then close the port and disconnect the node from the computer.

This opens the port; once the port is open, the button will change to Close. Clicking on Close will close your connection- so leave it open and click on the Local Console button on the left sidebar of the window (upper left corner, under the USB button).

With the port now open, you can click on Local Console to interact with your node in real-time.

Once in the Local Console section you’ll see three windows: Device Info, Tag Detections and Settings Summary. Each of these windows have associated menus and buttons.

Device info showing dropdown options

0.7.0.1 Device Info Window

Device Info provides several pieces of information by default:

  • BatteryVolts - current battery voltage
  • SolarCurrent - instantaneous information on solar current being pushed into the battery
  • SolarVolts - instantaneous information on solar voltage being received via the solar panel
  • TemperatureCelcius - the instantaneous temperature of the node board

At the bottom of the Device Info window there is a dropdown menu. Select any of the dropdown menu items and click the Submit button to issue a command to the node. Below are the menu items and their respective actions.

  • Serial Number - causes the Device Info window to display the DeviceID and Firmware version.

  • GPS Fix - causes the Node to take a GPS fix, and display the Latitude and Longitude in the Device Info window.

  • Health Report - causes the Node to transmit a health report. If a SensorStation is within range, the SensorStation should detect the health report. Note that there is no acknowledgment of success within Node Client.

  • Relay Beeps - causes the Node to transmit whatever beep data is currently in the buffer. If a SensorStation is within range, the SensorStation should detect the beep records. Note that there is no acknowledgment of success within Node Client.

  • Dynamics - this has no current application and is legacy option from a specific modified node that is not currently in production.

Here GPS Fix is selected from the dropdown, and the Submit button has been pressed, causing the Node to take a GPS fix and display the results in the Device Info window.

0.7.1 Tag Detections Window

If there are any tags within range of the node, you will see detection data populating in the Tag Detections window. These data include:

  • Detection Time (Local) - a date/time stamp in your local timezone.
  • Tag Id - the 8-digit tag ID from either a LifeTag, PowerTag or HybridTag
  • Signal (dBm) - the signal strength of the tag detection, measured in dBm, or the power level measured in decibels relative to one milliwatt.

While the Tag Detections window is pretty self explanatory, it also contains the button for updating the node firmware. If you have downloaded a more recent firmware version, you can load that firmware onto your node by pressing the Firmware button which will then open your file explorer. Updating the firmware is covered more extensively in the Updating Your Node Firmware section.

Pressing the Refresh button under the Settings Summary window causes the available settings to populate and gives you the opportunity to edit setting values.

0.7.2 Settings Summary Window

This window will initially be empty until you press the Refresh button. Once pressed, the available settings will populate the window, each with a gear button in the rightmost column.

To modify a setting’s parameter, click on the associated gear icon which will open a popup window specific to that setting.

Clicking on the gear icon in the rightmost cell of each setting row opens the parameterization window for that setting.

Here we have selected the RadioTxPower setting, which allows us to increase the power output of our onboard 434Mhz radio, thereby increasing the reach of our node to a nearby SensorStation. These parameters haven’t been fully documented, so please consult with before modifying settings unless otherwise specified in this guide. For instance, RadioTxPower can be modified up to 10dBm, but should not be set greater than that. To modify a value down below zero, use the negative value, for example, a value of -10 for RadioTxPower would reduce the power output by -10dBm.

Here you can modify the value, click Send, close the popup window, and then click Save and then Refresh at the bottom of the Settings Summary window.

To save these settings you first must click the Send button on the popup dialogue, and then click the Save button at the bottom of Settings Summary. To confirm that the settings have been set and saved, click the Refresh button at the bottom of theSettings Summary window.

If done correctly, you should see the setting value updated in the Settings Summary table.

Above you can see that the RadioTxPower has been successfully updated to +10dBm.

The Directory window in the File Transfer section.

0.7.3 File Transfer

Moving back to the left sidebar you see another button under Local Console; this one for File Transfer. Clicking on this button brings you to the Directory window.

Initially the window is empty, but clicking on Update in the upper right corner of the window will cause the console to list out all of the files on the SD card.

These are typically .csv files with either beep data, or gps data. From here you can either download or delete these files via the console.

Note: Since the USB transfer rate is very slow, it is recommended that you don’t use this console for downloading beep files, rather you can remove the SD card and use a 3rd party SD card reader to transfer these files to your computer, if desired.

Once you’re done working with your node, return to the USB section and click Close under Step 4. Now it is safe to disconnect your Node.

0.8 some other things